Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option to use vendored libgit2 #52

Merged
merged 4 commits into from
Sep 29, 2022
Merged

Add an option to use vendored libgit2 #52

merged 4 commits into from
Sep 29, 2022

Conversation

pacak
Copy link
Owner

@pacak pacak commented Sep 25, 2022

No description provided.

Copy link
Contributor

@dtolnay dtolnay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you consider making a cargo PR to expose vendored-libgit2 as a cargo feature? That way cargo-show-asm's vendored-libgit2 feature won't just silently stop working when cargo updates git2.

@pacak
Copy link
Owner Author

pacak commented Sep 25, 2022

Hmm... I would expect it to either keep working as long as they end up depending on the same foreign library or will stop compiling when it starts to depend on two of them, but yea, making a cargo request would be a better solution and not just for cargo-show-asm. Will look into that.

@pacak pacak merged commit 08409fe into master Sep 29, 2022
@pacak pacak deleted the vendored-libgit branch September 29, 2022 16:26
bors added a commit to rust-lang/cargo that referenced this pull request Sep 30, 2022
Expose libgit2-sys/vendored feature as vendored-libgit2

### What does this PR try to resolve?

Compiling cargo on MacOS can be problematic due present libraries, `cargo` already supports vendoring for openssl (and it helps pacak/cargo-show-asm#51 to some users). This pull request attempts to extend vendoring support to libgit2 in order to fix more foreign library issues: pacak/cargo-show-asm#50

While it is possible for me to enable it on my side (pacak/cargo-show-asm#52) a special care needs to keep versions in sync. Exposing this feature in `cargo` directly will make such fixes for my and other crates more robust.

### How should we test and review this PR?
Disabled by default means existing behavior is unchanged, testing with it enabled to confirm if it still works should do the trick.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants